feat(blueprints): add possibility enable/disable default brand #11738
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Details
Because ovveriding default brand is bit painful with docker/kubernetes
=> mount entpy file to replace
default-brand.yaml
can we instead add a env value like this,
will not breaking existing due to default fallback, but can be easily un defaulted what do you thiink ?
NB: this approch is IaC friendly
Checklist
None of them has been made du the minor change
not applicable i guess
ak test authentik/
)make lint-fix
)If an API change has been made
make gen-build
)If changes to the frontend have been made
make web
)If applicable
NB: will be done if accepted
make website
)